Service Interruption Reporting

ABSTRACT

There is provided mechanisms for service interruption reporting of a multicast bearer for group communications. A method is performed by a client node. The method comprises obtaining instruction from a control node of the multicast bearer, where the instruction instructs whether or not the client node is to report service interruption of the multicast bearer. The method comprises detecting service interruption of the multicast bearer. The method comprises selectively reporting the service interruption to the control node in accordance with the instruction.

RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.16/392,811 filed Apr. 24, 2019, which is a Continuation of U.S. patentapplication Ser. No. 15/539,178 filed Jun. 23, 2017 and issued as U.S.patent Ser. No. 10/348,552, which is the National Stage of InternationalPatent Application No. PCT/EP2016/076275 filed Nov. 1, 2016, thecontents of each of which are hereby incorporated by reference in theirentirety.

TECHNICAL FIELD

Embodiments presented herein relate to methods, a client node, a controlnode, computer programs, and a computer program product for serviceinterruption reporting of a multicast bearer for group communications.

BACKGROUND

In communications systems, there may be a challenge to obtain goodperformance and capacity for a given communications protocol, itsparameters and the physical environment in which the communicationssystem is deployed.

An example of applications available in some communications system isgroup communications services. In general terms, group communicationmeans that the same information or media is delivered to multiple clientnodes (as hosted by wireless devices).

In group communication systems the client nodes receiving the same mediaconstitute a group of client nodes. These client nodes may be located atdifferent locations in a radio coverage area served by one or more radioaccess network nodes. If many client nodes are located within the samearea, the one or more radio access network nodes could use multicast orbroadcast based transmission using e.g., Multicast-Broadcast MultimediaServices (MBMS) for efficient communication to the group of client nodessince communications resources, such as time and frequency resources,are shared among the client nodes.

Some activities are performed before MBMS can be used. One activityinvolves an MBMS bearer to be activated. This will enable media to besent over the network and broadcasted over the radio network to theclient nodes. In a third generation partnership project (3GPP) Long TermEvolution (LTE) network this is initiated in a Broadcast MulticastService Center (BMSC) as discussed in document 3GPP TS 23.246 v14.0.0.Another activity is to inform the client nodes of the service beingbroadcasted over the MBMS bearer. This activity is performed in orderfor the client nodes to know how to receive the media over the MBMSbearer. This procedure is commonly known as a service announcementprocedure and is discussed, e.g., in document 3GPP TS 26.346 v14.0.0which relates to service announcement in LTE networks.

MBMS provides a one-way communication channel, meaning that the data isbroadcasted from a radio access network node towards wireless deviceshosting client nodes. When a wireless device that receives data over anMBMS bearer is moving closer to the border of the broadcast area of theMBMS bearer in the radio access network node, the wireless device willrequest to receive the group communication data over a unicast bearerinstead of as before via broadcast.

However, there is a risk that the MBMS bearer is suspended or otherwiseinterrupted. Suspension of MBMS bearer could cause problems not only forthe client nodes but for the communications system as a whole. MBMSbearers are examples of multicast bearers.

US 2016/094358 A1 discloses a broadcast resource congestion controlmethod of a multi-cell/multicast coordination entity (MCE). Thedisclosure is concerned with notifying a group communication contentserver (GCS AS) as opposed to a multicast control node in order toinform this content source about an imminent suspension of a bearer.

3GPP TR 23.780 V1.1.0, 19 Oct. 2016, also relates to congestion relatedMBMS bearer suspension reporting by user equipment to a GCS AS.

EP 2 827 620 A1 is directed at network (e.g. eNodeB, MCE) initiatedservice status queries of, e.g. a wireless client, wherein the networksends MBMS service status queries to the wireless client, which areresponded to with MBMS status reports, these reports are concerned withMBMS service status rather than MBMS bearer suspension.

Hence, there is still a need for an improved handling of interruptionsof multicast bearers.

SUMMARY

An object of embodiments herein is to improve handling of interruptionsof a multicast bearer.

According to a first aspect there is presented a method for serviceinterruption reporting of a multicast bearer for group communications.The method is performed by a client node. The method comprises obtaininginstruction from a control node of the multicast bearer, where theinstruction instructs whether or not the client node is to reportservice interruption of the multicast bearer. The method comprisesdetecting service interruption of the multicast bearer. The methodcomprises selectively reporting the service interruption to the controlnode in accordance with the instruction.

Advantageously, this method (as well as the client nodes according tothe below second aspect, third aspect, and fourth aspect, and thecomputer program of the below fifth aspect) enables the client node toknow if it is to report any service interruption of the multicast beareror not.

According to a second aspect there is presented a client node forservice interruption reporting of a multicast bearer for groupcommunications, the client node comprising processing circuitry. Theprocessing circuitry is configured to cause the client node to obtaininstruction from a control node of the multicast bearer, where theinstruction instructs whether or not the client node is to reportservice interruption of the multicast bearer. The processing circuitryis configured to cause the client node to detect service interruption ofthe multicast bearer. The processing circuitry is configured to causethe client node to selectively report the service interruption to thecontrol node in accordance with the instruction.

According to a third aspect there is presented a client node for serviceinterruption reporting of a multicast bearer for group communications.The client node comprises processing circuitry and a storage medium. Thestorage medium stores instructions that, when executed by the processingcircuitry, cause the client node to perform operations, or steps. Theoperations, or steps, cause the client node to obtain instruction from acontrol node of the multicast bearer, where the instruction instructswhether or not the client node is to report service interruption of themulticast bearer. The operations, or steps, cause the client node todetect service interruption of the multicast bearer. The operations, orsteps, cause the client node to selectively report the serviceinterruption to the control node in accordance with the instruction.

According to a fourth aspect there is presented a client node forservice interruption reporting of a multicast bearer for groupcommunications. The client node comprises an obtain module configured toobtain instruction from a control node of the multicast bearer, wherethe instruction instructs whether or not the client node is to reportservice interruption of the multicast bearer. The client node comprisesa detect module configured to detect service interruption of themulticast bearer. The client node comprises a report module configuredto selectively report the service interruption to the control node inaccordance with the instruction.

According to a fifth aspect there is presented a computer program forservice interruption reporting of a multicast bearer for groupcommunications, the computer program comprising computer program codewhich, when run on processing circuitry of a client node, causes theclient node to perform a method according to the first aspect.

According to a sixth aspect there is presented a method for serviceinterruption reporting of a multicast bearer for group communications,the method being performed by a control node of the multicast bearer.The method comprises transmitting instruction whether or not a clientnode listening to the multicast bearer is to report service interruptionof the multicast bearer. The method comprises obtaining reporting ofservice interruption of the multicast bearer from the client nodeinstructed to report failure of the multicast bearer.

Advantageously, this method (as well as the control nodes according tothe below seventh aspect, eighth aspect, and ninth aspect, and thecomputer program of the below tenth aspect) enables the control node todetermine that less than all of the client nodes listening to themulticast bearer are to report any service interruption of the multicastbearer.

According to a seventh aspect there is presented a control node forservice interruption reporting of a multicast bearer for groupcommunications. The control node comprises processing circuitry. Theprocessing circuitry is configured to cause the control node to transmitinstruction whether or not a client node listening to the multicastbearer is to report service interruption of the multicast bearer. Theprocessing circuitry is configured to cause the control node to obtainreporting of service interruption of the multicast bearer from theclient node instructed to report failure of the multicast bearer.

According to an eighth aspect there is presented a control node forservice interruption reporting of a multicast bearer for groupcommunications. The control node comprises processing circuitry and astorage medium. The storage medium stores instructions that, whenexecuted by the processing circuitry, cause the control node to performoperations, or steps. The operations, or steps, cause the control nodeto transmit instruction whether or not a client node listening to themulticast bearer is to report service interruption of the multicastbearer. The operations, or steps, cause the control node to obtainreporting of service interruption of the multicast bearer from theclient node instructed to report failure of the multicast bearer.

According to a ninth aspect there is presented a control node forservice interruption reporting of a multicast bearer for groupcommunications. The control node comprises a transmit module configuredto transmit instruction whether or not a client node listening to themulticast bearer is to report service interruption of the multicastbearer. The control node comprises an obtain module configured to obtainreporting of service interruption of the multicast bearer from theclient node instructed to report failure of the multicast bearer.

According to a tenth aspect there is presented a computer program forservice interruption reporting of a multicast bearer for groupcommunications, the computer program comprising computer program codewhich, when run on processing circuitry of a control node, causes thecontrol node to perform a method according to the sixth aspect.

According to an eleventh aspect there is presented a computer programproduct comprising a computer program according to at least one of thefifth aspect and the tenth aspect and a computer readable storage mediumon which the computer program is stored. The computer readable storagemedium could be a non-transitory computer readable storage medium.

Advantageously these methods, these client nodes, these control nodes,and these computer programs enable efficient handling of interruptionsof multicast bearers.

Advantageously these methods, these client nodes, these control nodes,and these computer programs enable efficient notification reporting fromclient nodes that are listening on a multicast bearer, such as an MBMSbearer, particularly in scenarios where the multicast bearer issuspended, or by other means interrupted, and this interruption is knownto the client node as not being caused by network failure.

Advantageously these methods, these client nodes, these control nodes,and these computer programs reduce the risk of mass notification in MBMSfailure scenarios.

It is to be noted that any feature of the first, second, third, fourth,fifth, sixth seventh, eighth, ninth, tenth and eleventh aspects may beapplied to any other aspect, wherever appropriate. Likewise, anyadvantage of the first aspect may equally apply to the second, third,fourth, fifth, sixth, seventh, eighth, ninth, tenth, and/or eleventhaspect, respectively, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing detailed disclosure, from the attached dependent claims aswell as from the drawings.

Generally, all terms used in the claims are to be interpreted accordingto their ordinary meaning in the technical field, unless explicitlydefined otherwise herein. All references to “a/an/the element,apparatus, component, means, step, etc.” are to be interpreted openly asreferring to at least one instance of the element, apparatus, component,means, step, etc., unless explicitly stated otherwise. The steps of anymethod disclosed herein do not have to be performed in the exact orderdisclosed, unless explicitly stated.

BRIEF DESCRIPTION OF THE DRAWINGS

The inventive concept is now described, by way of example, withreference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram illustrating a communications systemaccording to embodiments;

FIGS. 2, 3, 4, and 5 are flowcharts of methods according to embodiments;

FIG. 6 is a signalling diagram of a method according to an embodiment;

FIG. 7 is a schematic diagram showing functional units of a client nodeaccording to an embodiment;

FIG. 8 is a schematic diagram showing functional modules of a clientnode according to an embodiment;

FIG. 9 is a schematic diagram showing functional units of a control nodeaccording to an embodiment;

FIG. 10 is a schematic diagram showing functional modules of a controlnode according to an embodiment; and

FIG. 11 shows one example of a computer program product comprisingcomputer readable means according to an embodiment.

DETAILED DESCRIPTION

The inventive concept will now be described more fully hereinafter withreference to the accompanying drawings, in which certain embodiments ofthe inventive concept are shown. This inventive concept may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided by way of example so that this disclosure will be thorough andcomplete, and will fully convey the scope of the inventive concept tothose skilled in the art. Like numbers refer to like elements throughoutthe description. Any step or feature illustrated by dashed lines shouldbe regarded as optional.

FIG. 1 is a schematic diagram illustrating a communications system 100where embodiments presented herein can be applied. The communicationssystem 100 is assumed to provide services for group communication andmay hence be regarded as a group communications system. The groupcommunications system 100 is, according to some aspects, a push to talk(PTT) system. The group communication could thus comprise a push to talkservice.

The communications system 100 comprises a radio access network (asrepresented by its radio coverage area 120), a core network 130, and aservice network 140. The communications system 100 further comprises atleast one control node 300 and at least one client node 200 a, 200 b,200 c. Each client node 200 a, 200 b, 200 c could be a mission critical(MC) service client. The at least one control node 300 may be providedin, or installed on, at least one radio access network (RAN) node 110 orin another entity or device in the radio access network, in an entity ordevice of the core network 130, or in an entity or device of the servicenetwork 140. The at least one control node 300 could implement thefunctionality of a group communication service application server (GCSAS) and be a MC service server. Each client node 200 a, 200 b, 200 c maybe hosted by, provided in, or installed on, a respective wireless device150 a, 150 b, 150 c.

The radio access network is operatively connected to the core network130 which in turn is operatively connected to the service network 140.The at least one radio access network node 110 thereby enables thewireless devices 150 a, 150 b, 150 c, and hence the client nodes 200 a,200 b, 200 c, to access services and exchange data as provided by theservice network 140. It is appreciated that core network 130 and theservice network 140 can be implemented on a common platform, i.e., notnecessarily on separate hardware.

Examples of wireless devices 150 a, 150 b, 150 c include, but are notlimited to, mobile stations, mobile phones, handsets, wireless localloop phones, user equipment (UE), smartphones, laptop computers, andtablet computers. Examples of radio access network nodes 110 include,but are not limited to, radio base stations, base transceiver stations,node Bs, evolved node Bs, and access points. As the skilled personunderstands, the communications system 100 may comprise a plurality ofradio access network nodes 110, each providing network access to aplurality of wireless devices 150 a, 150 b, 150 c. The herein disclosedembodiments are not limited to any particular number of radio accessnetwork nodes 110, client nodes 200 a, 200 b, 200 c, or wireless devices150 a, 150 b, 150 c.

As disclosed above, in a group communication system (e.g. a PTT system)it is common to use a broadcast technology such as MBMS. Using MBMSallows group communication data to be broadcasted while the wirelessdevices 150 a, 150 b, 150 c are in idle mode, i.e. only listening to thebroadcasted data.

In some communications systems the radio access network may suspend MBMSbearers without sending any MBMS bearer suspension decision informationto the control node 300. MBMS bearer suspension is described in 3GPP TS36.300 v14.0.0.

When using MBMS for group communications many client nodes 200 a, 200 b,200 c could be listening to the MBMS bearer. In a scenario where theMBMS bearer is suspended, or by other means is taken down, there couldthus be a risk that all client nodes 200 a, 200 b, 200 c simultaneouslyinitiate actions to re-initiate the communication. Such action mayinvolve establishing unicast transmission links between radio accessnetwork node 110 and wireless devices 150 a, 150 b, 150 c. This maycause an overload scenario due to too many client nodes 200 a, 200 b,200 c requesting network resources of the radio access network 120 atthe or approximately the same time.

In order to avoid such an overload scenario only a subset of the clientnodes 200 a, 200 b, 200 c can be configured to initiate unicasttransmission, whereas the remaining the client nodes 200 a, 200 b, 200 ccould be configured to refrain from initiating unicast transmission.Alternatively, some client nodes 200 a, 200 b, 200 c could be suspendedby the control node 300 from initiating unicast transmission. However,this could lead to uncertainties whether a particular client nodes 200a, 200 b, 200 c should initiate uncast transmission or not.

According to the embodiments disclosed herein the control node 300instructs the client nodes 200 a, 200 b, 200 c whether or not the clientnodes 200 a, 200 b, 200 c is to report service interruption. Theinstruction thereby causes only a subset of all client nodes 200 a, 200b, 200 c to report bearer failure in cases when the multicast bearerfailure is caused by a network issue. The embodiments disclosed hereinin particular relate to mechanisms for service interruption reporting ofa multicast bearer for group communications. In order to obtain suchmechanisms there is provided a client node 200 a, a method performed bythe client node 200 a, a computer program product comprising code, forexample in the form of a computer program, that when run on processingcircuitry of the client node 200 a, causes the client node 200 a toperform the method. In order to obtain such mechanisms there is furtherprovided a control node 300, a method performed by the control node 300,and a computer program product comprising code, for example in the formof a computer program, that when run on processing circuitry of thecontrol node 300, causes the control node 300 to perform the method.

FIGS. 2 and 3 are flow charts illustrating embodiments of methods forservice interruption reporting of a multicast bearer for groupcommunications as performed by the client node 200 a. FIGS. 4 and 5 areflow charts illustrating embodiments of methods for service interruptionreporting of a multicast bearer for group communications as performed bythe control node 300. The methods are advantageously provided ascomputer programs 1120 a, 1120 b (see, FIG. 11 below).

Reference is now made to FIG. 2 illustrating a method for serviceinterruption reporting of a multicast bearer for group communications asperformed by the client node 200 a according to an embodiment.

As will be disclosed below, the control node 300 in step S202 instructsthe client nodes 200 a, 200 b, 200 c whether or not to report serviceinterruption of the multicast bearer. Hence, the client node 200 a isconfigured to perform step S102:

S102: The client node 200 a obtains instruction from the control node300 of the multicast bearer. The instruction instructs whether or notthe client node 200 a is to report service interruption of the multicastbearer.

Examples of how and when the instruction could be obtained will beprovided below. The instruction obtained in step S102 could explicitlyinstruct the client node 200 a to report the service interruption to thecontrol node 300. Alternatively, there is no explicit instructionregarding to what network entity or node the client node 200 a is toreport the service interruption to and in such cases the client node 200a could be configured to assume that the service interruption is to bereported to the sender of the instruction, namely the control node 300.

It is assumed that there is a service interruption of the multicastbearer. Hence, the client node 200 a is configured to perform step S108:

S108: The client node 200 a detects service interruption of themulticast bearer.

Examples of service interruption will be provided below. Such a serviceinterruption could be detected by all client nodes 200 a, 200 b, 200 clistening to the multicast bearer. But according to the instructionobtained in step s102 not all client nodes 200 a, 200 b, 200 c are toreport the service interruption to the control node 300. Particularly,the client node 200 a is configured to report the service interruptionaccording to step S110:

S110: The client node 200 a selectively reports the service interruptionto the control node 300 in accordance with the instruction. That is, toselectively report is here to be understood as the client node 200 areports the service interruption if the instruction obtained in stepS102 instructs the client node 200 a to do so and refrains from suchreporting if the instruction obtained in step S102 instructs the clientnode 200 a to not report the service interruption. That is, theinstruction could instruct not only those client nodes that are toreport the service interruption to actually do so, but also to instructthose client nodes that are not to report the service interruption toactually not to report the service interruption. Hence, although allclient nodes 200 a, 200 b, 200 c may obtain the instructions in stepS102, not all client nodes 200 a, 200 b, 200 c will report the serviceinterruption in step S110.

Embodiments relating to further details of service interruptionreporting of a multicast bearer for group communications as performed bythe client node 200 a will now be disclosed.

Reference is now made to FIG. 3 illustrating methods for serviceinterruption reporting of a multicast bearer for group communications asperformed by the client node 200 a according to further embodiments. Itis assumed that steps S102, S108, S110 are performed as described abovewith reference to FIG. 2 and a thus repeated description thereof istherefore omitted.

There could be different ways for the client node 200 a to obtain theinstruction in step S102. According to an embodiment the instruction isobtained during a service announcement procedure of the multicastbearer. According to another embodiment the instruction is obtained in aservice announcement update of the multicast bearer, where the serviceannouncement update could be based on a listening report. The serviceannouncement procedure and the listening report could be performed asdiscussed in 3GPP TS 23.179 v13.3.0 (where the listening report iscalled MBMS listening status report). As an example, the instruction instep S102 could be obtained as a request for an MBMS suspension reportand the service announcement procedure could be an MBMS bearerannouncement procedure.

There could be different ways for the client node 200 a to report theservice interruption in step S110. According to an embodiment theservice interruption is reported in a multicast bearer suspensionreport. According to another embodiment the service interruption isreported in a multicast bearer in a listening report. As an example, theinstruction obtained in step S102 could instruct the client node 200 ato report the service interruption in an MBMS suspension report.

According to some aspects, all client nodes 200 a, 200 b, 200 clistening to the multicast bearer could report their current location tothe control node 300. As will be further disclosed below, such locationinformation could by the control node 300 be used to determine whichclient nodes that are to report the service interruption. Hence,according to an embodiment the instruction further instructs the clientnode 200 a to report location and the client node 200 a is configured toperform step S104:

S104: The client node 200 a reports location of the client node 200 a tothe control node 300 in accordance with the instruction. The reportingof location could be performed periodically when the client node 200 alistens to the multicast bearer.

There could be ways for the control node 300 a to keep track of thoseclient nodes 200 a that are instructed to report service interruption ofthe multicast bearer.

According to some aspects the client node 200 a continuously sendskeepalive (KA) signals to the control node 300. Such KA signals could bythe control node 300 be used to verify that the client node 200 a stilllistens to the multicast bearer and hence still is capable of detectingservice interruption of the multicast bearer. Thus, it is appreciatedthat a KA signal can be any signal which enables the control node 300 toverify that the client node 200 a is still capable of detecting serviceinterruption of the multicast bearer. Hence, according to an embodimentthe instruction further instructs the client node 200 a to send KAsignals if the client node 200 a is instructed to report serviceinterruption of the multicast bearer and the client node 200 a isconfigured to perform step S106:

S106: The client node 200 a selectively sends the KA signals to thecontrol node in accordance with the instruction. Selectively sends ishere to be construed as in the above discussed step of selectivelyreporting (S110).

Absence of KA signals from a client node 200 a instructed to send KAsignals could by the control node 300 be used to conclude that theclient node 200 a no longer is capable of detecting service interruptionof the multicast bearer, and/or is no longer able to report serviceinterruption.

According to some aspects the client node 200 a reports to the controlnode 300 if the client node 200 a is shut down or is about to be shutdown. Such a report of the shutdown of the client node 200 a could bythe control node 300 be used to conclude that the client node 200 a nolonger is capable of detecting service interruption of the multicastbearer and/or is no longer able to report service interruption. Hence,according to an embodiment the instruction further instructs the clientnode 200 a to report shutdown if the client node 200 a is instructed toreport service interruption of the multicast bearer and the client node200 a is configured to perform step S112:

S112: The client node 200 a selectively reports shutdown of the clientnode 200 a to the control node 300 in accordance with the instruction.Selectively report here has the same understanding as the abovedisclosed selectively report in step S110.

Shutdown is here to be construed broadly to incorporate anyconfiguration or re-configuration of the client node 200 a which ispreventing the client node 200 a from detecting service interruption ofthe multicast bearer and/or from reporting service interruption.Examples include, e.g., selectively disabling a radio transceiver or thewireless device 150 a, for example by setting the wireless device 160 inso called flight mode, or knowingly entering a location with poor ornon-existent network coverage, such as going underground or into atunnel (with the wireless device 150 a).

It is understood that there could be scenarios where the client node 200a is unable to perform such reporting, such as if the power source ofthe client node 200 a is suddenly removed. In such cases the controlnode 300 could rely on receiving KA signals from the client node 200 aas disclosed above and hence be configured to assume that the clientnode 200 a is shut off if KA signals are no longer sent from the clientnode 200 a.

There could be different ways for the client node 200 a to detect theservice interruption. According to some aspects the client node 200 areceives a suspension indication from the radio access network node 110.Hence, according to an embodiment the client node 200 a is configured todetect the service interruption of the multicast bearer in step S108 byperforming step S108 a:

S108 a: The client node 200 a obtains a suspension indication of themulticast bearer from a radio access network node 110 of the multicastbearer.

Step S108 a could be performed as part of step S108.

The suspension indication could be included in a scheduling informationpacket.

Reference is now made to FIG. 4 illustrating a method for serviceinterruption reporting of a multicast bearer for group communications asperformed by the control node 300 according to an embodiment.

As disclosed above, according to the embodiments disclosed herein thecontrol node 300 instructs the client nodes 200 a, 200 b, 200 c whetheror not the client nodes 200 a, 200 b, 200 c is to report serviceinterruption. Hence, the control node 300 is configured to perform stepS202:

S202: The control node 300 transmits instruction whether or not a clientnode 200 a, 200 b, 200 c listening to the multicast bearer is to reportservice interruption of the multicast bearer.

The instruction could comprise identification information, such anaddress, an identity, or any other information that uniquely could beused to identify a subset of those client nodes 200 a, 200 b, 200 c thatare to report service interruption of the multicast bearer. This couldhelp the control node 300 to keep track of which client nodes 200 a, 200b, 200 c that are to report service interruption of the multicast bearerand which client nodes 200 a, 200 b, 200 c that are to not reportservice interruption of the multicast bearer.

As disclosed above, the client node 200 a in a step S110 reports theservice interruption to the control node 300. Hence, the control node300 is configured to perform step S204:

S204: The control node 300 obtains reporting of service interruption ofthe multicast bearer from the client node 200 a instructed to reportfailure of the multicast bearer.

Embodiments relating to further details of service interruptionreporting of a multicast bearer for group communications as performed bythe control node 300 will now be disclosed.

Reference is now made to FIG. 5 illustrating methods for serviceinterruption reporting of a multicast bearer for group communications asperformed by the control node 300 according to further embodiments. Itis assumed that steps S202, S204 are performed as described above withreference to FIG. 4 and a thus repeated description thereof is thereforeomitted.

There may be different ways for the control node 300 to transmit theinstruction in step S202. As disclosed above, the instruction could betransmitted during a service announcement procedure of the multicastbearer or in a service announcement update of the multicast bearer.Hence, according to an embodiment the instruction is broadcast during aservice announcement procedure of the multicast bearer or in a serviceannouncement update of the multicast bearer. In general terms, theservice announcement provides information to the client nodes 200 a, 200b, 200 c on the identity of the multicast bearer and how to receive theservice over the multicast bearer. The multicast bearer serviceannouncement message may be transmitted by a unicast transmission toeach client node 200 a, 200 b, 200 c or in a broadcast message to allclient nodes 200 a, 200 b, 200 c in the radio coverage area 120.

According to some aspects only subset of the client nodes 200 a, 200 b,200 c are to report the service interruption. Hence, according to anembodiment the instruction instructs only a selected subset of clientnodes 200 a, 200 b, 200 c to report service interruption of themulticast bearer. The control node 300 may thus be configured totransmitting the instruction in step S202 to a subset of all the clientnodes 200 a, 200 b, 200 c. Client nodes that are not part of the subsetare thus not to report the service interruption.

There could be different ways for the control node 300 to select howmany client nodes 200 a, 200 b, 200 c are to be members of the subset.

According to some aspects the number of members in the subset is basedon the total number of client nodes 200 a, 200 b, 200 c. Hence,according to an embodiment the number of members of the selected subsetis based on the total number of client nodes 200 a, 200 b, 200 clistening to the multicast bearer. As an example, the subset couldcomprise of a fixed percentage, such as in the range of 10%, of thetotal number of client nodes 200 a, 200 b, 200 c listening to themulticast bearer.

Further, there could be different ways for the control node 300 toselect which client nodes 200 a, 200 b, 200 c are to be members of thesubset. Consideration could be taken to the location of the client nodes200 a, 200 b, 200 c, since location of the client nodes 200 a, 200 b,200 c could be dynamically changed. According to some aspects whichclient nodes 200 a, 200 b, 200 c to be members of the subset istherefore based on the service area (e.g., based on location informationof the client nodes 200 a, 200 b, 200 c as reported by the client nodes200 a, 200 b, 200 c in step S104). Hence, according to an embodiment themembers of the selected subset are selected based on locationinformation as obtained by the control node 300 from the client nodes200 a, 200 b, 200 c. This means that the instruction transmitted to theclient nodes 200 a, 200 b, 200 c for reporting service interruption mayneed to be updated based on new members entering the multicast bearerservice area (and hence being part of the subset). Hence, the controlnode 300 could be configured to transmit the instruction as in step S202upon the subset having been updated. Hence, the control node 300 couldreevaluate the subset of client nodes 200 a, 200 b, 200 c based on thelocation information reported from the client nodes 200 a, 200 b, 200 cin step S104 which thus is dynamically updated when the client nodes 200a, 200 b, 200 c move. That is, according to an embodiment the controlnode 300 is configured to update the subset based on a pre-defined setof rules. One such rule could be based on the location of the clientnodes 200 a, 200 b, 200 c listening to the multicast bearer.Alternatively, the members of the selected subset are randomly selected(out of the client nodes 200 a, 200 b, 200 c listening to the multicastbearer). Hence, another rule could be that the members of the selectedsubset are randomly selected when the subset of client nodes 200 a, 200b, 200 c is updated. Another rule could be based on any combination ofthe rules mentioned above.

Embodiments relating to mechanisms for the control node 300 to keeptrack of which client nodes 200 a, 200 b, 200 c are listening to themulticast bearer have been disclosed above.

There could be different ways for the control node 300 upon havingobtained reporting of the service interruption in step S204.

According to some aspects the control node 300 responds to the reportingby moving the service of the multicast bearer to another bearer. Hence,according to an embodiment a service is sent on the multicast bearer andthe control node 300 is configured to perform steps S206, S208 uponhaving obtained the reporting of service interruption in step S204:

S206: The control node 300 moves the service to another bearer.

S208: The control node 300 transmits a service announcement of thisanother bearer.

The so-called another bearer could be a multicast bearer or a unicastbearer. Step S208 could be omitted if the bearer is a unicast bearer.

According to some aspects the control node 300 responds to the reportingby queuing the service until the multicast bearer is resumed. Hence,according to an embodiment a service is sent on the multicast bearer andthe control node 300 is configured to perform step S210 upon havingobtained the reporting of service interruption in step S204:

S210: The control node 300 queues the service until the multicast beareris resumed or until another bearer is available for sending the service.

According to some aspects the control node 300 responds to the reportingby selecting to suspend certain low prioritized services and setting upunicast bearers only to high priority services. Hence, according to anembodiment a service is sent on the multicast bearer and the controlnode 300 is configured to perform step S212 upon having obtained thereporting of service interruption in step S204:

S212: The control node 300 moves the service to a unicast bearer.

There could be different reasons for the service interruption. Accordingto some aspects the service interruption is caused by bearer failure.Hence, according to an embodiment the service interruption is caused bymulticast bearer failure detected by the client nodes 200 a, 200 b, 200c. There could be different events causing the bearer failure. As anexample the multicast bearer could be suspended or pre-empted. If themulticast bearer is subjected to strong interference then the clientnode 200 a and/or wireless device 150 a could just report this asexperiencing a network performance degradation in a listening report.

There could be different examples of multicast bearers. According to anembodiment the multicast bearer is an MBMS bearer.

One particular embodiment for service interruption reporting of amulticast bearer (provided as an MBMS bearer) for group communicationsbased on at least some of the above disclosed embodiments will now bedisclosed in detail with reference to the signalling diagram of FIG. 6.

S301: The MBMS bearer is activated by the control node 300 and the RANnode 110.

S302: During an MBMS bearer announcement procedure instructions are sentfrom the control node 300 (via the RAN node 110) to client nodes 200 a,200 b, 200 c to at least some of the client nodes 200 a, 200 b, 200 c toreport detection of MBMS bearer outage. In the illustrative examples itis assumed that client node 200 a is instructed to report detection ofMBMS bearer outage.

S303: The RAN node 110 decides to suspend the MBMS bearer. In a 3GPPbased network the RAN node 110 transmits a suspension indicator suchthat the client nodes 200 a, 200 b, 200 c (via its hosting wirelessdevice 150 a, 150 b, 150 c) can detect that the MBMS bearer has beensuspended. The RAN node 110 could decide to suspend the MBMS beareraccording to existing procedures in 3GPP TS 36.300 v14.0.0.

S304: The RAN node 110 sends an MBMS suspension indication. The MBMSsuspension indication could be sent in the MSI (Multicast channelScheduling Information) according to existing procedures in 3GPP TS36.300 v14.0.0. The client nodes 200 a, 200 b, 200 c are thereby enabledto detect that the MBMS bearer has been suspended.

S305: The client node 200 a that has received instruction to send anMBMS bearer suspension notification to the group communication serversends this notification to the control node 300 in an MBMS bearersuspension report.

S306: The control node 300, optionally, based on receiving thenotification sent in step S305, informs all client nodes 200 a, 200 b,200 c in the MBMS service area of alternative ways of receiving the MBMSservice by sending an MBMS bearer service announcement.

FIG. 7 schematically illustrates, in terms of a number of functionalunits, the components of a client node 200 a according to an embodiment.Processing circuitry 210 is provided using any combination of one ormore of a suitable central processing unit (CPU), multiprocessor,microcontroller, digital signal processor (DSP), etc., capable ofexecuting software instructions stored in a computer program product1110 a (as in FIG. 11), e.g. in the form of a storage medium 230. Theprocessing circuitry 210 may further be provided as at least oneapplication specific integrated circuit (ASIC), or field programmablegate array (FPGA).

Particularly, the processing circuitry 210 is configured to cause theclient node 200 a to perform a set of operations, or steps, S102-S112,as disclosed above. For example, the storage medium 230 may store theset of operations, and the processing circuitry 210 may be configured toretrieve the set of operations from the storage medium 230 to cause theclient node 200 a to perform the set of operations. The set ofoperations may be provided as a set of executable instructions. Thus theprocessing circuitry 210 is thereby arranged to execute methods asherein disclosed.

The storage medium 230 may also comprise persistent storage, which, forexample, can be any single one or combination of magnetic memory,optical memory, solid state memory or even remotely mounted memory.

The client node 200 a may further comprise a communications interface220 for communications at least with the control node 300. As such thecommunications interface 220 may comprise one or more transmitters andreceivers, comprising analogue and digital components.

The processing circuitry 210 controls the general operation of theclient node 200 a e.g. by sending data and control signals to thecommunications interface 220 and the storage medium 230, by receivingdata and reports from the communications interface 220, and byretrieving data and instructions from the storage medium 230. Othercomponents, as well as the related functionality, of the client node 200a are omitted in order not to obscure the concepts presented herein.

FIG. 8 schematically illustrates, in terms of a number of functionalmodules, the components of a client node 200 a according to anembodiment. The client node 200 a of FIG. 8 comprises a number offunctional modules; an obtain module 210 a configured to perform stepS102, a detect module 210 d configured to perform step S108, and areport module 210 f configured to perform step S110. The client node 200a of FIG. 8 may further comprise a number of optional functionalmodules, such as any of a report module 210 b configured to perform stepS104, a send module 210 c configured to perform step S106, an obtainmodule 210 e configured to perform step S108 a, and a report module 210g configured to perform step S112. In general terms, each functionalmodule 210 a-210 g may be implemented in hardware or in software.Preferably, one or more or all functional modules 210 a-210 g may beimplemented by the processing circuitry 210, possibly in cooperationwith functional units 220 and/or 230. The processing circuitry 210 maythus be arranged to from the storage medium 230 fetch instructions asprovided by a functional module 210 a-210 g and to execute theseinstructions, thereby performing any steps of the client node 200 a asdisclosed herein.

In general terms, each functional module 210 a-210 g may in oneembodiment be implemented only in hardware or and in another embodimentwith the help of software, i.e., the latter embodiment having computerprogram instructions stored on the storage medium 230 which when run onthe processing circuitry makes the client node 200 a perform thecorresponding steps mentioned above in conjunction with FIGS. 2 and 3.It should also be mentioned that even though the modules correspond toparts of a computer program, they do not need to be separate modulestherein, but the way in which they are implemented in software isdependent on the programming language used. Preferably, one or more orall functional modules 210 a-210 g may be implemented by the processingcircuitry 210, possibly in cooperation with functional units 220 and/or230. The processing circuitry 210 may thus be configured to from thestorage medium 330 fetch instructions as provided by a functional module210 a-210 g and to execute these instructions, thereby performing anysteps as disclosed herein.

The client node 200 a may be provided as a standalone device or as apart of at least one further device. For example, the client node 200 amay be hosted by, provided in, or installed on a wireless device 150 a.

FIG. 9 schematically illustrates, in terms of a number of functionalunits, the components of a control node 300 according to an embodiment.Processing circuitry 310 is provided using any combination of one ormore of a suitable central processing unit (CPU), multiprocessor,microcontroller, digital signal processor (DSP), etc., capable ofexecuting software instructions stored in a computer program product1110 b (as in FIG. 11), e.g. in the form of a storage medium 330. Theprocessing circuitry 310 may further be provided as at least oneapplication specific integrated circuit (ASIC), or field programmablegate array (FPGA).

Particularly, the processing circuitry 310 is configured to cause thecontrol node 300 to perform a set of operations, or steps, S202-S212, asdisclosed above. For example, the storage medium 330 may store the setof operations, and the processing circuitry 310 may be configured toretrieve the set of operations from the storage medium 330 to cause thecontrol node 300 to perform the set of operations. The set of operationsmay be provided as a set of executable instructions. Thus the processingcircuitry 310 is thereby arranged to execute methods as hereindisclosed.

The storage medium 330 may also comprise persistent storage, which, forexample, can be any single one or combination of magnetic memory,optical memory, solid state memory or even remotely mounted memory.

The control node 300 may further comprise a communications interface 320for communications at least with the client nodes 200 a, 200 b, 200 c.As such the communications interface 320 may comprise one or moretransmitters and receivers, comprising analogue and digital components.

The processing circuitry 310 controls the general operation of thecontrol node 300 e.g. by sending data and control signals to thecommunications interface 320 and the storage medium 330, by receivingdata and reports from the communications interface 320, and byretrieving data and instructions from the storage medium 330. Othercomponents, as well as the related functionality, of the control node300 are omitted in order not to obscure the concepts presented herein.

FIG. 10 schematically illustrates, in terms of a number of functionalmodules, the components of a control node 300 according to anembodiment. The control node 300 of FIG. 10 comprises a number offunctional modules; a transmit module 310 a configured to perform stepS202, and an obtain module 310 b configured to perform step S204. Thecontrol node 300 of FIG. 10 may further comprise a number of optionalfunctional modules, such as any of a move module 310 c configured toperform step S206, a transmit module 310 d configured to perform stepS208, a queue module 310 e configured to perform step S210, and a movemodule 310 f configured to perform step S212. In general terms, eachfunctional module 310 a-310 f may be implemented in hardware or insoftware. Preferably, one or more or all functional modules 310 a-310 fmay be implemented by the processing circuitry 310, possibly incooperation with functional units 320 and/or 330. The processingcircuitry 310 may thus be arranged to from the storage medium 330 fetchinstructions as provided by a functional module 310 a-310 f and toexecute these instructions, thereby performing any steps of the controlnode 300 as disclosed herein.

In general terms, each functional module 310 a-310 f may in oneembodiment be implemented only in hardware or and in another embodimentwith the help of software, i.e., the latter embodiment having computerprogram instructions stored on the storage medium 330 which when run onthe processing circuitry makes the control node 300 perform thecorresponding steps mentioned above in conjunction with FIGS. 4 and 5.It should also be mentioned that even though the modules correspond toparts of a computer program, they do not need to be separate modulestherein, but the way in which they are implemented in software isdependent on the programming language used. Preferably, one or more orall functional modules 310 a-310 f may be implemented by the processingcircuitry 310, possibly in cooperation with functional units 320 and/or330. The processing circuitry 310 may thus be configured to from thestorage medium 330 fetch instructions as provided by a functional module310 a-310 f and to execute these instructions, thereby performing anysteps as disclosed herein.

The control node 300 may be provided as a standalone device or as a partof at least one further device. For example, the control node 300 may behosted by, provided in, or installed on a GCS AS or an MC serviceserver.

FIG. 11 shows one example of a computer program product 1110 a, 1110 bcomprising computer readable means 1130. On this computer readable means1130, a computer program 1120 a can be stored, which computer program1120 a can cause the processing circuitry 210 and thereto operativelycoupled entities and devices, such as the communications interface 220and the storage medium 230, to execute methods according to embodimentsdescribed herein. The computer program 1120 a and/or computer programproduct 1110 a may thus provide means for performing any steps of theclient node 200 a as herein disclosed. On this computer readable means1130, a computer program 1120 b can be stored, which computer program1120 b can cause the processing circuitry 310 and thereto operativelycoupled entities and devices, such as the communications interface 320and the storage medium 330, to execute methods according to embodimentsdescribed herein. The computer program 1120 b and/or computer programproduct 1110 b may thus provide means for performing any steps of thecontrol node 300 as herein disclosed.

In the example of FIG. 11, the computer program product 1110 a, 1110 bis illustrated as an optical disc, such as a CD (compact disc) or a DVD(digital versatile disc) or a Blu-Ray disc. The computer program product1110 a, 1110 b could also be embodied as a memory, such as a randomaccess memory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM), or an electrically erasable programmableread-only memory (EEPROM) and more particularly as a non-volatilestorage medium of a device in an external memory such as a USB(Universal Serial Bus) memory or a Flash memory, such as a compact Flashmemory. Thus, while the computer program 1120 a, 1120 b is hereschematically shown as a track on the depicted optical disk, thecomputer program 1120 a, 1120 b can be stored in any way which issuitable for the computer program product 1110 a, 1110 b.

The inventive concept has mainly been described above with reference toa few embodiments. However, as is readily appreciated by a personskilled in the art, other embodiments than the ones disclosed above areequally possible within the scope of the inventive concept, as definedby the appended patent claims.

What is claimed is:
 1. A method for service interruption reporting of amulticast bearer for group communications, the method being performed bya client node, the method comprising: obtaining instruction from acontrol node of the multicast bearer, where the instruction instructswhether or not the client node is to report service interruption of themulticast bearer; detecting service interruption of the multicastbearer; and selectively reporting the service interruption to thecontrol node in accordance with the instruction.
 2. The method accordingto claim 1, wherein the instruction is obtained during a serviceannouncement procedure of the multicast bearer.
 3. The method accordingto claim 1, wherein detecting service interruption of the multicastbearer comprises: obtaining a suspension indication of the multicastbearer from a radio access network node of the multicast bearer.
 4. Themethod according to claim 1, wherein the service interruption isreported in a multicast bearer suspension report or in a listeningreport.
 5. The method according to claim 1, wherein the instructionfurther instructs the client node to report location, the method furthercomprising: reporting location of the client node to the control node inaccordance with the instruction.
 6. The method according to claim 1,wherein the instruction further instructs the client node to sendkeepalive (KA) signals if the client node is instructed to reportservice interruption of the multicast bearer, the method furthercomprising: selectively sending the KA signals to the control node inaccordance with the instruction.
 7. The method according to claim 1,wherein the instruction further instructs the client node to reportshutdown if the client node is instructed to report service interruptionof the multicast bearer, the method further comprising: selectivelyreporting shutdown of the client node to the control node in accordancewith the instruction.
 8. A method for service interruption reporting ofa multicast bearer for group communications, the method being performedby a control node of the multicast bearer, the method comprising:transmitting instruction whether or not a client node listening to themulticast bearer is to report service interruption of the multicastbearer; and obtaining reporting of service interruption of the multicastbearer from the client node instructed to report failure of themulticast bearer.
 9. The method according to claim 8, wherein theinstruction is broadcast during a service announcement procedure of themulticast bearer.
 10. The method according to claim 8, wherein theinstruction instructs a selected subset of client nodes to reportservice interruption of the multicast bearer.
 11. The method accordingto claim 10, wherein number of members of the selected subset is basedon total number of client nodes listening to the multicast bearer. 12.The method according to claim 10, wherein members of the selected subsetare selected based on location information obtained from the clientnodes.
 13. The method according to claim 10, wherein members of theselected subset are randomly selected.
 14. The method according to claim8, wherein a service is sent on the multicast bearer, the method furthercomprising, upon having obtained the reporting of service interruption:moving the service to another bearer; and transmitting a serviceannouncement of said another bearer.
 15. The method according to claim8, wherein a service is sent on the multicast bearer, the method furthercomprising, upon having obtained the reporting of service interruption:queuing the service until the multicast bearer is resumed or untilanother bearer is available for sending the service.
 16. The methodaccording to claim 8, wherein a service is sent on the multicast bearer,the method further comprising, upon having obtained the reporting ofservice interruption: moving said service to a unicast bearer.
 17. Themethod according to claim 1, wherein the service interruption is causedby multicast bearer failure detected by the client nodes.
 18. The methodaccording to claim 1, wherein the multicast bearer is a MultimediaBroadcast Multicast Services (MBMS) bearer.
 19. A client node forservice interruption reporting of a multicast bearer for groupcommunications, the client node comprising: processing circuitry; and astorage medium storing instructions that, when executed by theprocessing circuitry, cause the client node to: obtain instruction froma control node of the multicast bearer, where the instruction instructswhether or not the client node is to report service interruption of themulticast bearer; detect service interruption of the multicast bearer;and selectively report the service interruption to the control node inaccordance with the instruction.
 20. A control node for serviceinterruption reporting of a multicast bearer for group communications,the control node comprising: processing circuitry; and a storage mediumstoring instructions that, when executed by the processing circuitry,cause the control node to: transmit instruction whether or not a clientnode listening to the multicast bearer is to report service interruptionof the multicast bearer; and obtain reporting of service interruption ofthe multicast bearer from the client node instructed to report failureof the multicast bearer.
 21. A non-transitory computer readablerecording medium storing a computer program product for serviceinterruption reporting of a multicast bearer for group communications,the computer program product comprising software instructions which,when run on processing circuitry of a client node, causes the clientnode to: obtain instruction from a control node of the multicast bearer,where the instruction instructs whether or not the client node is toreport service interruption of the multicast bearer; detect serviceinterruption of the multicast bearer; and selectively report the serviceinterruption to the control node in accordance with the instruction. 22.A non-transitory computer readable recording medium storing a computerprogram product for service interruption reporting of a multicast bearerfor group communications, the computer program product comprisingsoftware instructions which, when run on processing circuitry of acontrol node, causes the control node to: transmit instruction whetheror not a client node listening to the multicast bearer is to reportservice interruption of the multicast bearer; and obtain reporting ofservice interruption of the multicast bearer from the client nodeinstructed to report failure of the multicast bearer.